System and method for controlling access to legacy short message peer-to-peer protocols based upon a policy

ABSTRACT

In accordance with embodiments, there are provided mechanisms and methods for controlling access to telecommunications resources implementing a legacy protocol based upon a policy. These mechanisms and methods for controlling access to legacy protocols based upon a policy can enable embodiments to control access by third party created and other applications to network resources implementing legacy telecommunications protocols. The ability of embodiments to control access by third party created and other applications to network resources can enable network providers to provide greater access to network resources without compromising security of other users. Embodiments may further provide the ability to interface with legacy push protocols, multimedia message protocols and short message peer-to-peer protocols.

CLAIM OF PRIORITY

The present application claims the benefit of U.S. Provisional PatentApplication No. 60/733,823, entitled SYSTEM AND METHOD FOR A GATEKEEPERIN A COMMUNICATIONS NETWORK, by Reto Kramer, et al., filed on Nov. 4,2005 (Attorney Docket No. BEAS-1962US0), which is incorporated herein byreference in its entirety.

CROSS REFERENCE TO RELATED APPLICATIONS

The following commonly owned, co-pending United States Patents andPatent Applications, including the present application, are related toeach other. Each of the other patents/applications are incorporated byreference herein in their entirety:

U.S. patent application Ser. No. 11/378,188, entitled SYSTEM AND METHODFOR MANAGING COMMUNICATIONS SESSIONS IN A NETWORK, by Reto Kramer, etal., filed on Mar. 17, 2006 (Attorney Docket No. BEAS-1744US1);

U.S. patent application Ser. No. 11/384,056, entitled SYSTEM AND METHODFOR A GATEKEEPER IN A COMMUNICATIONS NETWORK, by Reto Kramer, et al.,filed on Mar. 17, 2006 (Attorney Docket No. BEAS-1962US1);

U.S. patent application Ser. No. ______ entitled SYSTEM AND METHOD FOR[Diameter], by Anno Langen, et al., filed on May XX, 2006 (AttorneyDocket No. BEAS-2057US0);

U.S. patent application Ser. No. ______ entitled SYSTEM AND METHOD FOR[SIP/HTTP CONVERGENCE], by Anno Langen, et al., filed on May _(—), 2006(Attorney Docket No. BEAS-2060US0);

U.S. patent application Ser. No. ______ entitled SYSTEM AND METHOD FOR[HITLESS APPLICATION UPGRADE], by Jaroslaw Wilkiewicz, et al., filed onMay _(—), 2006 (Attorney Docket No. BEAS-2061US0);

U.S. patent application Ser. No. ______ entitled SYSTEM AND METHOD FOR[ENGINE NEAR CACHE], by Anno Langen, et al., filed on May XX, 2006(Attorney Docket No. BEAS-2062US0);

U.S. patent application Ser. No. ______ entitled SYSTEM AND METHOD FORCONTROLLING DATA FLOW BASED ON A TEMPORAL POLICY, by Narendra Vemula, etal., filed on May _(—), 2006 (Attorney Docket No. BEAS-2064US0);

U.S. patent application Ser. No. ______ entitled SYSTEM AND METHOD FORCONTROLLING ACCESS TO LEGACY PUSH PROTOCOLS BASED UPON A POLICY, byBengt-Inge Jakobsson, et al., filed on May _(—), 2006 (Attorney DocketNo. BEAS-2066US0);

U.S. patent application Ser. No. ______ entitled SYSTEM AND METHOD FORCONTROLLING ACCESS TO LEGACY MULTIMEDIA MESSAGE PROTOCOLS BASED UPON APOLICY, by Andreas Jansson, filed on May _(—), 2006 (Attorney Docket No.BEAS-2067US0);

U.S. patent application Ser. No. ______ entitled SYSTEM AND METHOD FORCONTROLLING ACCESS TO LEGACY SHORT MESSAGE PEER-TO-PEER PROTOCOLS BASEDUPON A POLICY, by Andreas Jansson, filed on May _(—), 2006 (AttorneyDocket No. BEAS-2068US0); and

U.S. patent application Ser. No. ______ entitled SYSTEM AND METHOD FORSHAPING TRAFFIC, by Jan Svensson, filed on May _(—), 2006 (AttorneyDocket No. BEAS-2070US0).

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

FIELD OF THE INVENTION

The current invention relates generally to managing telecommunicationsand more particularly to a mechanism for controlling access to legacyshort message peer-to-peer protocols based upon a policy.

BACKGROUND

Conventionally, telecommunications and network infrastructure providershave relied on often decades old switching technology to providingrouting for network traffic. Businesses and consumers, however, aredriving industry transformation by demanding new converged voice, dataand video services. The ability to meet these demands often can belimited by existing IT and network infrastructures that are closed,proprietary and too rigid to support these next generation services. Asa result, telecommunications companies are transitioning fromtraditional, circuit-switched Public Switched Telephone Networks (PSTN),the common wired telephone system used around the world to connect anyone telephone to another telephone, to Voice Over Internet Protocol(VoIP) networks. VoIP technologies enable voice communication over“vanilla” IP networks, such as the public Internet. Additionally, asteady decline in voice revenues has resulted in heightened competitivepressures as carriers vie to grow data/service revenues and reduce churnthrough the delivery of these more sophisticated data services.Increased federal regulation, security and privacy issues, as well asnewly emerging standards can further compound the pressure.

However, delivering these more sophisticated data services has proved tobe more difficult than first imagined. Existing IT and networkinfrastructures, closed proprietary network-based switching fabrics andthe like have proved to be too complex and too rigid to allow thecreation and deployment of new service offerings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1B are illustrations of an example communications platform thatcan be used to control access to legacy push protocols based upon apolicy in an embodiment.

FIGS. 2A-2B are illustrations of example functional aspects of acommunications platform embodiment.

FIGS. 3A-3C are operational flow diagrams illustrating a high leveloverview of techniques for controlling access to legacy protocols basedupon a policy in an embodiment.

FIGS. 4A-4C are illustrations of example functional aspects of a legacyprotocol coupled with a communications platform embodiment.

FIGS. 5A-5C are illustrations of example usage scenarios of legacyprotocols in embodiments.

DETAILED DESCRIPTION

The invention is illustrated by way of example and not by way oflimitation in the figures of the accompanying drawings in which likereferences indicate similar elements. References to embodiments in thisdisclosure are not necessarily to the same embodiment, and suchreferences mean at least one. While specific implementations arediscussed, it is understood that this is done for illustrative purposesonly. A person skilled in the relevant art will recognize that othercomponents and configurations may be used without departing from thescope and spirit of the invention.

In the following description, numerous specific details are set forth toprovide a thorough description of the invention. However, it will beapparent to those skilled in the art that the invention may be practicedwithout these specific details. In other instances, well-known featureshave not been described in detail so as not to obscure the invention.

Although a diagram may depict components as logically separate, suchdepiction is merely for illustrative purposes. It can be apparent tothose skilled in the art that the components portrayed can be combinedor divided into separate software, firmware and/or hardware components.For example, one or more of the embodiments described herein can beimplemented in a network accessible device/appliance such as a router.Furthermore, it can also be apparent to those skilled in the art thatsuch components, regardless of how they are combined or divided, canexecute on the same computing device or can be distributed amongdifferent computing devices connected by one or more networks or othersuitable communication means.

In accordance with embodiments, there are provided mechanisms andmethods for controlling access to telecommunications resourcesimplementing a legacy protocol based upon a policy. These mechanisms andmethods for controlling access to legacy protocols based upon a policycan enable embodiments to control access by third party created andother applications to network resources implementing legacytelecommunications protocols. The ability of embodiments to controlaccess by third party created and other applications to networkresources can enable network providers to provide greater access tonetwork resources without compromising security of other users.Embodiments may further provide the ability to interface with legacypush protocols, multimedia message protocols and short messagepeer-to-peer protocols.

In an aspect and according to embodiments, there are provided mechanismsand methods for controlling access to telecommunications resourcesimplementing a legacy push protocol based upon a policy. In anembodiment and by way of example, a telecommunications system isprovided. A system embodiment includes an application interface toreceive at least one invocation to a legacy push protocol from a legacyapplication. A gatekeeper controls access through the telecommunicationssystem by applying at least one policy to the invocation. The at leastone policy indicates whether the legacy application is permitted to usea resource of the telecommunications system. A resource interfaceconnecting the gatekeeper with at least one resource elementimplementing the legacy push protocol receives the at least oneinvocation to a legacy push protocol when the gatekeeper permits thelegacy application to use a resource of the telecommunications system.

In another aspect and according to embodiments, there are providedmechanisms and methods for controlling access to telecommunicationsresources implementing a legacy multimedia message protocol based upon apolicy. In an embodiment and by way of example, a telecommunicationssystem is provided. A system embodiment includes an applicationinterface to receive at least one invocation to a legacy multimediamessage protocol from a legacy application. A gatekeeper controls accessthrough the telecommunications system by applying at least one policy tothe invocation. The at least one policy indicates whether the legacyapplication is permitted to use a resource of the telecommunicationssystem. A resource interface connects the gatekeeper with at least oneresource element implementing the legacy multimedia message protocol toreceive the at least one invocation to a legacy multimedia messageprotocol when the gatekeeper permits the legacy application to use aresource of the telecommunications system.

In a yet further aspect and according to embodiments, there are providedmechanisms and methods for controlling access to telecommunicationsresources implementing a legacy short message peer-to-peer protocolbased upon a policy. In an embodiment and by way of example, atelecommunications system is provided. A system embodiment includes anapplication interface to receive at least one invocation to a legacyshort message peer-to-peer protocol from a legacy application. Agatekeeper controls access through the telecommunications system byapplying at least one policy to the invocation. The at least one policyindicates whether the legacy application is permitted to use a resourceof the telecommunications system. A resource interface connects thegatekeeper with at least one resource element implementing the legacyshort message peer-to-peer protocol to receive the at least oneinvocation to a legacy short message peer-to-peer protocol when thegatekeeper permits the legacy application to use a resource of thetelecommunications system.

As used herein, the terms service and web service are usedinterchangeably and are intended to be broadly construed to include anyapplication, program or process resident on one or more computingdevices capable of providing services to a requestor or other recipient,including without limitation network based applications, web basedserver resident applications, web portals, search engines, photographic,audio or video information storage applications, e-Commerceapplications, backup or other storage applications, sales/revenueplanning, marketing, forecasting, accounting, inventory managementapplications and other business applications and other contemplatedcomputer implemented services. As used herein, the term applicationbroadly includes any data entry, update, query or program that processesdata on behalf of a user. Users may be human or computational entities.

As used herein, the term web services protocol is defined as acommunications protocol that can be used for providing services betweentwo or more applications over a network. Typical web services protocolsinclude without limitation Short Message Peer-to-Peer protocol (SMPP)protocol, Push Application Protocol (PAP) protocol, Multimedia MessagingServices (MM7) protocol and Internet Message Access Protocol (IMAP)protocol. As used herein, the term legacy protocol is defined as acommunications protocol implemented by existing applications ortelecommunications systems.

As used herein, the term legacy push protocol is defined as a legacyprotocol used by applications to push data to a client device, such aswithout limitation Push Application Protocol (PAP) for example. The PushAccess Protocol (PAP), defined by the Wireless Application Protocol(WAP) Forum, outlines a proactive way to send information from Internetservers to WAP enabled mobile devices without the user having toactively request it. Typical use cases include alerts to which the userhas subscribed, small ads, and email notifications. Combined with otherapplications, such as location-based services, push becomes a flexibleway of providing users with real-time information. For example andwithout limitation, a tourist service could use push messaging toautomatically inform a user of interesting sites nearby and suggest theclosest restaurant according to predefined preferences and even providesa link to order a table.

As used herein, the term legacy multimedia message protocol is definedas a legacy protocol used by an application to exchange multimedia datato a client device, such as without limitation Multimedia MessageProtocol 7 (MM7) for example. Multimedia Messaging Service (MMS) enablesthe addition of images, text, audio clips and ultimately, video clips toSMS (Short Message Service/text messaging). MMS implementations mayoffer a development and billing environments. The MM7 protocol providesa mechanism for sending value-added service content from those thirdparties to subscribers who have MMS-enabled mobile devices. The MM7protocol defines and manages the data interface and protocols for thecommunication between Value-Added Service Providers (VASPs), whichgenerate the multimedia message content, and carriers, which deliver thecontent to a recipient device or forward it to a remote carrier fordelivery

As used herein, the term legacy short message peer-to-peer protocol isdefined as a legacy protocol used by applications to exchange data inshort messages with one another, such as without limitation ShortMessage Peer-To-Peer Protocol (SMPP) for example. The SMPP version 3.4,for example and without limitation, is a Short Message Peer to PeerProtocol that is an open, industry standard protocol designed to providea flexible data communications interface for transfer of short messagedata between a Message Center such as a Short Message Service Center(SMSC), Global System for Mobile communications (GSM) UnstructuredServices Data (USSD) Server or other type of message center and amessage center and a SMS application system. This includes WAP ProxyServer, email gateway, or other messaging gateway.

As used herein, the term legacy application is defined as an applicationdesigned to interface with a legacy protocol. As used herein, the termresource interface is defined as a mechanism to provide access forservices to reach callers and end user applications (clients) via anetwork. As used herein, the term resource element is defined as anetwork resource that implements a protocol within a network, such aswithout limitation Short Message Service (SMS), Multimedia MessageService (MMS) for example and others.

FIG. 1A is an illustration of an example communications platform thatcan be used to control access to legacy push protocols based upon apolicy in an embodiment. Although this diagram depicts components aslogically separate, such depiction is merely for illustrative purposes.It will be apparent to those skilled in the art that the componentsportrayed in this figure can be arbitrarily combined or divided intoseparate software, firmware and/or hardware. Furthermore, it will alsobe apparent to those skilled in the art that such components, regardlessof how they are combined or divided, can execute on the same computingdevice or can be distributed among different computing devices connectedby one or more networks or other suitable communication means.

A SIP server 102 and a network gatekeeper 104 comprise a portfolio ofproduct collectively comprise a communications platform 100. The SIPserver 102 provides the communications platform 100 with a subsystem inwhich application components that interact with SIP-based networks maybe deployed. The network gatekeeper 104 provides a policy-driventelecommunications Web services gateway that allows granular controlover access to network resources from un-trusted domains.

A variety of shared and re-usable software and service infrastructurecomponents comprise the communications platform 100. For example, anapplication server, such as the WebLogic™ Application Server by BEASystems, Inc. of San Jose, Calif. This application server may beaugmented and adapted for deployment in telecommunications networks,while providing many features and functionality of the WebLogic™ Servercounterpart widely deployed in enterprise computing environments.Application server embodiments for use in the telecommunicationsapplications can provide a variety of additional features andfunctionality, such as without limitation:

-   -   Optimized for Peak Throughput    -   Clustering for Scalability and High-Performance    -   Generalized for wide range of target platforms (HW/OS) support    -   Extensive deployment configuration options    -   Optimized for local management    -   Plug and play Enterprise Information Systems (EIS) support

Analogously, communications platform embodiments can provide a varietyof additional features and functionality, such as without limitation:

-   -   Highly Deterministic Runtime Environment    -   Clustering for High-Availability (HA) and Scalability    -   Optimized for Telecom HW/OS/HAM W platforms support (SAF, ATCA,        HA M/W, etc.)    -   Hardened configuration    -   Optimized for Telecom NMS integration    -   Telecommunications network connectors and interfaces

FIG. 1B is another illustration of an example communications platformthat can be used to control access to legacy push protocols based upon apolicy in an embodiment. Although this diagram depicts components aslogically separate, such depiction is merely for illustrative purposes.It will be apparent to those skilled in the art that the componentsportrayed in this figure can be arbitrarily combined or divided intoseparate software, firmware and/or hardware. Furthermore, it will alsobe apparent to those skilled in the art that such components, regardlessof how they are combined or divided, can execute on the same computingdevice or can be distributed among different computing devices connectedby one or more networks or other suitable communication means.

Communications platform 100 comprises a Session Initiation Protocol(SIP) Server (WLSS) 102 and a Network Gatekeeper (WLNG) 104. Tools forinteracting with Web Services, such as a Web Service-UniversalDescription Discovery Interface (WS/UDDI) 110, a Web Service-BusinessProcess Execution Language (WS/BPEL) 112 may be coupled to the SIPServer 102 and the Network Gatekeeper 104 in embodiments. A log/traceand database 114 can assist with troubleshooting. In some deployments,the communications platform 100 can interface with processes thatmonitor underlying network function, such as Operations SupportSystems/Business Support Systems (OSS/BSS) system 120 via RA protocoladapters 122. (RA protocol is a protocol for submission of billinginformation that are maintained in the network gatekeeper 104 and sentto a carrier's existing billing infrastructure.) Embodiments can includeone or more of the following services OSS/BSS services. For example andwithout limitation, Operations Support Systems services can includeactivation, service assurance, usage/metering and provisioning,including designing, assigning and inventory. Business Support Systemscan include billing, including invoicing, rating, taxation, andcollections 124, customer management, including order entry, customerself services, customer care, trouble ticketing, and customerrelationship management. Such interfaces can provide access toOperation, Administration, and Maintenance (OAM) applications 126 andothers. A policy engine 103 controls access by one or more third partyservices (not shown) and services (not shown) to resource elements (notshown) in a network layer.

A Service Creation Environment (SCE) enables service providers to createapplications using a higher level programming abstraction tool toexpedite application creation. Other types of tools may be provided inembodiments to enable internal staff who are not necessarily softwareengineers (e.g. business analysts, IT/MIS staff) but are programmers orhave programming skills (e.g. internal software engineers with knowledgeof the carrier's network etc. but perhaps less savvy as high power J2EEsoftware engineers) to be able to create or modify applications.

A communications platform embodiment can provide an open, highperformance, software based fault-tolerant platform that allowsoperators to maximize revenue potential by shortening time to market andsignificantly reducing per-service implementation and integration costand complexity. The communications platform is suitable for use by fornetwork infrastructure vendors, network operators and communicationsservice providers in multiple deployment scenarios ranging from fully IPmulti-media subsystem (IMS) oriented network architectures to hybrid andhighly heterogeneous network architectures. It is not restricted to useonly in carrier networks, however, and may be deployed in Enterprisecommunications networks without restriction or extensive customization.When deployed in conjunction with an IP multimedia subsystem, thecommunications platform can serve in the role of an IMS SIP applicationserver and offers communications service providers an executionenvironment in which to host applications (such as the WebLogic™ NetworkGatekeeper), components and standard service enablers. The followingdiagrams illustrate example network gatekeeper embodiments intelecommunications systems.

FIG. 2A in an illustration of example functional aspects of acommunications platform embodiment. Although this diagram depictscomponents as logically separate, such depiction is merely forillustrative purposes. It will be apparent to those skilled in the artthat the components portrayed in this figure can be arbitrarily combinedor divided into separate software, firmware and/or hardware.Furthermore, it will also be apparent to those skilled in the art thatsuch components, regardless of how they are combined or divided, canexecute on the same computing device or can be distributed amongdifferent computing devices connected by one or more networks or othersuitable communication means.

As illustrated by FIG. 2A and by way of example, an embodiment of acommunications platform 100 provides an easy to use, integrated,configuration-driven intermediary between service providers 134, thirdparty service providers 138 and end users 136. The communicationsplatform 100 embodiment illustrated by FIG. 2A comprises an applicationlayer 200 with interfaces to applications of the service providers 134and third party service providers 138 and a network layer 220 tointerface with the end users 136 via one or more network resourceelements 221. Communications platform 100 further comprises a gatekeeperlayer 210 interposed between the application layer 200 and the networklayer 220 for managing and controlling information flowing betweenlayers 200 and 220.

At the application layer 200, third party service providers 138 andservice providers 134 are provided protocol adapters 206-209 to makeservices 201-203 available to callers over a network via the gatekeeperlayer 210 provided by the communications platform 100. Access to networkresource elements 221 by services 201, 202, 203 may be achieved usingone or more web services protocol adapters 206-209. The protocoladapters 206-209 provide an interface mechanism, enabling the networkgatekeeper 104 to intercept protocol communications from services201-203 and control access to network resource elements by the services201-203 in accordance with one or more policies. While illustrated herewith reference to an embodiment having adapters to specific protocols,including without limitation, a Short Message Peer-to-Peer protocol(SMPP) protocol adapter 206, a Push Application Protocol (PAP) protocoladapter 207, a Multimedia Messaging Services (MM7) protocol adapter 208and an Internet Message Access Protocol (IMAP) protocol adapter 209,embodiments may include any number or kind of protocols and are neitherlimited to, nor required to possess, these illustrated protocoladapters.

The gatekeeper layer 210 includes a gatekeeper 104 that comprises aplurality of functional elements working in concert to control access tonetwork resource elements 221 at the network layer 220 by services201-203 according to one or more policies. In an embodiment, a servicelevel agreement (SLA) 214 comprises one or more policies governingaccess to the network layer 220. A policy engine 103 providesenforcement of the service level agreements. Service level agreementsspecify, e.g., how many messages customer A sends an hour, and if over acontract limit, customer A starts paying more, and so forth. In oneembodiment, capabilities to create, customize, and execute service levelagreement provisions as policies are provided. A charging mechanism 215determines charges to callers for making a call using network resourceelements 221, e.g., determine charges for network traffic (i.e., calls)according to charging information payment amount/schedule, priorities,and the like. Charging mechanism 215 may access data including Call DataRecords (CDR) and/or Event Data Records (EDR) in order to determinecharges. In one embodiment, the charging mechanism 215 determines anallocation of charges to be apportioned to the third party providing theservice. As shown by the dotted lines in FIG. 2A, the actions of thepolicy engine 103 and other functional elements of the gatekeeper 104provide virtual isolation layers 212 a, 212 b between services 201-203at the application layer 200 and network resource elements 221 at thenetwork layer 220. The isolation layers 212 a, 212 b indicate that thegatekeeper layer 210 functional elements can be isolated from, andunaffected by, the particulars of protocols, interfaces and the likeused by applications, services and callers communicating using thenetwork via the gatekeeper 104.

The gatekeeper layer 210 may include one or more resource interfaces 211to interface with legacy protocols 216-218 or other web servicesprotocols 219 as a mechanism to reach callers and end user applications(clients) via the network layer 220. While illustrated here withreference having resource interfaces to specific protocols, includingwithout limitation, an SMPP protocol adapter 216, a PAP protocol adapter217, an MM7 protocol adapter 218 and an IMAP protocol adapter 219,embodiments may include any number or kind of protocols and are neitherlimited to, nor required to possess, these illustrated resourceinterfaces. An extension toolkit (not shown) enables partners to developresource interfaces for other protocols to include into the gatekeeperlayer 210.

Network layer 220 includes one or more resource elements 221 such aswithout limitation a Parlay (protocol) gateway 222, an IMS (IPmulti-media subsystem) 223, an SMSCs (short-message-service-center) 224and MMSCs (multi-media messaging service center) 225, each of whichprovides a mechanism for moving information through the network to oneor more end user services 136.

FIG. 2B is functional block diagram that shows a high level overview ofan example logical architecture in which techniques for managingservices in a communications network may be embodied. By way of exampleand as illustrated by FIG. 2B, communications platform 100 of FIG. 2Amay be implemented using multi-tier system architecture. As shown inFIG. 2B, an example multi-tier system architecture provides independent,coordinated execution of business logic implementing services and thelike, executing in one tier, and communications connection managementlogic which executes in a second tier. An application tier 252 comprisesmachines capable of executing applications, including applicationsprovided by third parties, on behalf of callers that initiatecommunications sessions managed by the network tier 254. In anembodiment, an interconnection mechanism 253 provides an interconnectionbetween network elements of application tier 252 and network tier 254.In an example embodiment, interconnection mechanism 253 comprises JavaMessaging Service (JMS). In an alternate embodiment, interconnectionmechanism 253 is implemented using Common Object Request BrokerArchitecture (CORBA), a group of application programming interfaces(APIs), communication protocols, and object/service information modelsto enable heterogeneous applications written in various languagesrunning on various platforms to interoperate.

FIG. 3A is an operational flow diagram illustrating a high leveloverview of a technique for controlling access to legacy push protocolsbased upon a policy in an embodiment. The technique for controllingaccess to legacy push protocols based upon a policy shown in FIG. 3A isoperable with a network gatekeeper, such as network gatekeeper 104 ofFIG. 1A and FIG. 1B, for example. As shown in FIG. 3A, at least oneinvocation to a legacy push protocol is received from a legacyapplication by an application interface (block 302). For example andwithout limitation, this can include receiving at least one invocationto a legacy push application protocol (PAP) from a legacy application.

A network gatekeeper controls access through the telecommunicationssystem by applying at least one policy to the invocation (block 304).The at least one policy indicates whether the legacy application ispermitted to use a resource of the telecommunications system. By way ofexample and without limitation, this can include controlling accessthrough the telecommunications system with a policy engine at agatekeeper by applying at least one policy in accordance with a servicelevel agreement (SLA) to the invocation.

A resource interface connecting the gatekeeper with at least oneresource element implementing the legacy push message protocol isprovided the at least one invocation to a legacy push message protocolwhen the gatekeeper permits the legacy application to use a resource ofthe telecommunications system (block 306). In embodiments, this caninclude receiving, the at least one invocation to a legacy push protocolat a resource interface plug-in connecting the gatekeeper with at leastone resource element implementing the legacy push application protocol(PAP) when the gatekeeper permits the legacy application to use aresource of the telecommunications system for example.

FIG. 3B is an operational flow diagram illustrating a high leveloverview of a technique for controlling access to legacy multimediaprotocols based upon a policy in an embodiment. The technique forcontrolling access to legacy multimedia protocols based upon a policyshown in FIG. 3B is operable with a network gatekeeper, such as networkgatekeeper 104 of FIG. 1A and FIG. 1B, for example. As shown in FIG. 3B,at least one invocation to a legacy multimedia message protocol isreceived from a legacy application by an application interface (block312). For example and without limitation, this can include receiving atleast one invocation to a legacy multimedia message services protocol(MM7) from a legacy application.

A network gatekeeper controls access through the telecommunicationssystem by applying at least one policy to the invocation. The at leastone policy indicates whether the legacy application is permitted to usea resource of the telecommunications system (block 314). By way ofexample and without limitation, this can include controlling accessthrough the telecommunications system with a policy engine at agatekeeper by applying at least one policy in accordance with a servicelevel agreement (SLA) to the invocation.

A resource interface connecting the gatekeeper with at least oneresource element implementing the legacy multimedia message protocol isprovided the at least one invocation to a legacy multimedia messageprotocol when the gatekeeper permits the legacy application to use aresource of the telecommunications system (block 316). In embodiments,this can include receiving the at least one invocation to a legacymultimedia message protocol at a resource interface plug-in connectingthe gatekeeper with at least one resource element implementing thelegacy multimedia message services protocol (MM7) when the gatekeeperpermits the legacy application to use a resource of thetelecommunications system for example.

FIG. 3C is an operational flow diagram illustrating a high leveloverview of a technique for controlling access to legacy short messagepeer-to-peer protocols based upon a policy in an embodiment. Thetechnique for controlling access to legacy short message peer-to-peerprotocols based upon a policy shown in FIG. 3C is operable with anetwork gatekeeper, such as network gatekeeper 104 of FIG. 1A and FIG.1B, for example. As shown in FIG. 3C, at least one invocation to alegacy short message peer-to-peer protocol is received from a legacyapplication by an application interface (block 322). For example andwithout limitation, this can include receiving at least one invocationto a legacy Short Message Peer-to-Peer Protocol (SMPP) from a legacyapplication.

A network gatekeeper controls access through the telecommunicationssystem by applying at least one policy to the invocation. The at leastone policy indicates whether the legacy application is permitted to usea resource of the telecommunications system (block 324). By way ofexample and without limitation, this can include controlling accessthrough the telecommunications system with a policy engine at agatekeeper by applying at least one policy in accordance with a servicelevel agreement (SLA) to the invocation.

A resource interface connecting the gatekeeper with at least oneresource element implementing the legacy short message peer-to-peerprotocol is provided the at least one invocation to a legacy shortmessage peer-to-peer protocol when the gatekeeper permits the legacyapplication to use a resource of the telecommunications system (block326). In embodiments, this can include receiving the at least oneinvocation to a legacy short message peer-to-peer protocol at a resourceinterface plug-in connecting the gatekeeper with at least one resourceelement implementing the legacy Short Message Peer-to-Peer Protocol(SMPP) when the gatekeeper permits the legacy application to use aresource of the telecommunications system.

Push Application Protocol (PAP)

FIG. 4A is an illustration of example functional aspects of a legacypush protocol coupled with a communications platform embodiment. A PushInitiator residing on an Internet server to access a push proxy gatewayuses the Push Access protocol. The Push Access Protocol is designed tobe independent of the underlying transport protocol. A messaging pipe410 a routes a push application protocol message from a push initiator401 a to network elements 422 a. In this example, the PAP interface 407a communicates with an ESPA module 412 a. The ESPA module 412 b thencommunicates with a plug in manager (not shown) for the PAP Plug-inresource interface 417 a. The PAP Plug-in resource interface 417 aprovides connectivity to the network elements 422 a. Network elements422 a may provide connectivity to a push proxy gateway that pushes themessages to clients.

FIG. 5A illustrates an example usage scenario of the PAP Protocol in anembodiment. The Push Initiator 501 interfaces directly with thegatekeeper 514 to initiate an application layer connection for sendingpush messages. The gatekeeper 514 controls message traffic between thepush initiator 501 and push proxy gateway 536. Push proxy gateway 536pushes the messages to the consumer clients 538.

The response and result notification is used by the push proxy gateway536 to inform the push initiator 501 of the final outcome of a pushsubmission, if requested by the push initiator 501. This notificationtells the push initiator 501 that the message was sent, delivered(confirmation received from wireless device), expired, cancelled, orthere was an error. If there was a processing error, the notificationcan be sent immediately upon detection of the error to the pushinitiator 501 and the message should not be sent to the client.Otherwise, the notification will be sent after the message deliveryprocess has been completed. The delivery process is considered completedwhen the message is no longer a candidate for delivery, e.g. the messagehas expired. If the push submission is indicated as rejected, then noresult notification will be sent.

Gatekeeper embodiments can provide Quality of Service, SLAs-Policyenforcement, traffic throttling, Service Provider/Applicationauthentication and others. Embodiments can ensure that carrier networkelements are used in the most optimal and controlled manner when Pushmessages are submitted to a push proxy gateway.

Multimedia Messaging Protocol (MM7)

FIG. 4B is an illustration of example functional aspects of a legacymultimedia messaging protocol coupled with a communications platformembodiment. A messaging pipe 412 b routes the message from a clientapplication 401 b to the network elements 425 b. In this example, theMM7 interface 408 a communicates with a SESPA module. The SESPA modulein turn routes message/comments via the ESPA layer 412 b. The ESPA layer412 b in turn communicates with the plug in manager (not shown) of theMM7 Plug-in resource interface 418 b. The MM7 Plug-in resource interface418 a provides connectivity to the network elements 425 b. Networkelements 425 b may provide connectivity to end user clients.

FIG. 5B illustrates an example usage scenario of the MM7 Protocol in anembodiment. In the usage scenario illustrated by FIG. 5B, the networkgatekeeper 554 is shown integrated as part of a MM7 architecture. Theapplications 551 will interface directly with the network gatekeeper 554to initiate an application layer connection for sending multimediamessages. The gatekeeper 554 controls message traffic between theapplication 551 and MMSC 555. The MMSC 555 provides connectivity to theconsumer clients 556.

The gatekeeper embodiments can provide Quality of Service, SLAs-Policyenforcement, traffic throttling, Service Provider/Applicationauthentication and others. Embodiments can ensure that carrier networkelements are used in the most optimal and controlled manner whenmultimedia messages are sent to the MMSC.

Short Message Peer-to-Peer Protocol (SMPP)

FIG. 4C is an illustration of example functional aspects of a legacyshort message peer-to-peer protocol coupled with a communicationsplatform embodiment. FIG. 4C illustrates a messaging pipe 410 c thatroutes a short peer-to-peer message from the application 401 c tonetwork elements 422 c. In this example, the SMPP interface 406 ccommunicates with an ESPA module 412 c. The ESPA module 412 c thencommunicates with a plug in manager (not shown) for the SMPP Plug-inresource interface 416 c. The SMPP Plug-in resource interface 416 cprovides connectivity to the network elements 424 c.

If a short message is too long to fit inside one SUBMIT_SM operation atthe client on which the application 401 c resides, the SMPP Client willsplit the message and send it using multiple SUBMIT_SM operations. TheSMPP interface 406 c will collect the multiple SUBMIT_SM operations andturn them into one sendSMS call towards ESPA module 412 c. Later when aprocessNotification call is made by ESPA module 412 c to indicate thatthe message was delivered, the SMPP interface 406 c will send multipleDELIVER_SM operations to the SMPP Client, i.e. multiple deliveryreceipts. This is when there were multiple messages that were sent.

FIG. 5C illustrates an example usage scenario of the SMPP Protocol in anembodiment. An SMS application system called the “External Short MessageEntity” (ESME) 561 may initiate an application layer connection via thegatekeeper 566 with an SMSC 568 over a TCP/IP” or “X.25” networkconnection and may then send short messages and receive short messagesto and from the SMSC 568 respectively. The EMSE may query, cancel, orreplace short messages using SMPP.

Applications such as WAP Proxy Client, VMS and Paging Bureau willinterface directly with the gatekeeper. The gatekeeper embodiments canprovide Quality of Service, SLAs-Policy enforcement, traffic throttling,Service Provider/Application authentication and others. Embodiments canensure that carrier network elements are used in the most optimal andcontrolled manner when SMS messages are exchanged with the SMSC.

In other aspects, the invention encompasses in some embodiments,computer apparatus, computing systems and machine-readable mediaconfigured to carry out the foregoing methods. In addition to anembodiment consisting of specifically designed integrated circuits orother electronics, the present invention may be conveniently implementedusing a conventional general purpose or a specialized digital computeror microprocessor programmed according to the teachings of the presentdisclosure, as will be apparent to those skilled in the computer art.

Appropriate software coding can readily be prepared by skilledprogrammers based on the teachings of the present disclosure, as will beapparent to those skilled in the software art. The invention may also beimplemented by the preparation of application specific integratedcircuits or by interconnecting an appropriate network of conventionalcomponent circuits, as will be readily apparent to those skilled in theart.

The present invention includes a computer program product which is astorage medium (media) having instructions stored thereon/in which canbe used to program a computer to perform any of the processes of thepresent invention. The storage medium can include, but is not limitedto, any type of rotating media including floppy disks, optical discs,DVD, CD-ROMs, microdrive, and magneto-optical disks, and magnetic oroptical cards, nanosystems (including molecular memory ICs), or any typeof media or device suitable for storing instructions and/or data.

Stored on any one of the machine readable medium (media), the presentinvention includes software for controlling both the hardware of thegeneral purpose/specialized computer or microprocessor, and for enablingthe computer or microprocessor to interact with a human user or othermechanism utilizing the results of the present invention. Such softwaremay include, but is not limited to, device drivers, operating systems,and user applications.

Included in the programming (software) of the general/specializedcomputer or microprocessor are software modules for implementing theteachings of the present invention, including, but not limited toproviding mechanisms and methods for controlling access to legacy pushprotocols based upon a policy as discussed herein.

Various embodiments may be implemented using a conventional generalpurpose or specialized digital computer(s) and/or processor(s)programmed according to the teachings of the present disclosure, as canbe apparent to those skilled in the computer art. Appropriate softwarecoding can readily be prepared by skilled programmers based on theteachings of the present disclosure, as can be apparent to those skilledin the software art. The invention may also be implemented by thepreparation of integrated circuits and/or by interconnecting anappropriate network of conventional component circuits, as can bereadily apparent to those skilled in the art.

Embodiments can provide, by way of example and without limitation,services such as:

VoIP services, including, without limitation the following features:

Basic features. These include standards services such as Voice mail,Caller ID, Call waiting, and call forwarding (the ability to forward acall to a different number).

Advanced features. The list of advanced features is operators specific.Following is a brief list of advanced features:

Call logs: The ability to view calls made over a given period of timeonline, ability to associate names with phone numbers, integrate calllog information to other applications such as IM.

Do not disturb: The ability to specify policies around receivingcalls—for example, all calls during office hours to be automaticallyforwarded to a mobile terminal, all calls during the night to bedirected to voice mail etc.

Locate me: This is advanced call forwarding. Rather than have all callsforwarded to a single location (e.g., voice mail) when the caller isbusy, Locate me can try multiple terminals in series or in parallel. Forexample, a user may have two office locations, a mobile, and a pager,and it may make sense to forward a call to both office locations first,then the pager, and then the mobile terminal. Locate me is anotherexample of feature interaction.

Personal conferencing: A user could use an existing application (e.g.,IM client) to schedule a Web/audio conference to start at a certaintime. Since the IM client already has personal profile information, theconferencing system sends out the Web conference link information eitherthrough IM and/or email to the participants. The phone contactinformation in the profile is used to automatically ring theparticipants at the time of the conference.

Lifetime number: This is the facility where a single virtual number cantravel with a customer wherever they live. Even if they move, the oldnumber continues to work, and reaches them at their new location. Thisis really the analog of static IP addresses in a phone network.

Speed dial: This is the ability to dramatically expand the list ofnumbers that can be dialed through short-key and acceleratorcombinations. This is another example of a converged application, sinceit's very likely that when a user will set up this information when theywork through the call logs on the operator user portal, and the updatedinformation needs to be propagated to the network side in real-time.

Media delivery services, including, without limitation the followingfeatures:

Depending on the service level agreement users are willing to sign upto, the quality of media delivered (e.g. #of frames per second) willvary. The policy engine enables segmenting the customer base by revenuepotential, and to maximize return on investment made in the network.

Context-sensitive applications including, without limitation thefollowing features:

A typical example here is the need for applications that have a shortlifetime, extremely high usage peaks within their lifetime, andimmediacy. For example, voting on American Idol during the show orimmediately afterwards has proved to be an extremely popularapplication.

Integrated applications including, without limitation the followingfeatures:

The final class of applications is one that combines wireline andwireless terminal usage scenarios. An example of an integratedapplication is the following: a mobile terminal user is on a conferencecall on their way to work. When he reaches his office, he enters aspecial key sequence to transfer the phone call to his office phone. Thetransfer happens automatically without the user having to dial in thedial-in information again. It's important to note hear that thiscapability be available without the use of any specific support from thehand-set (a transfer button for example).

Various embodiments include a computer program product which is astorage medium (media) having instructions stored thereon/in which canbe used to program a general purpose or specialized computingprocessor(s)/device(s) to perform any of the features presented herein.The storage medium can include, but is not limited to, one or more ofthe following: any type of physical media including floppy disks,optical discs, DVDs, CD-ROMs, microdrives, magneto-optical disks,holographic storage, ROMs, RAMs, PRAMS, EPROMs, EEPROMs, DRAMs, VRAMs,flash memory devices, magnetic or optical cards, nanosystems (includingmolecular memory ICs); paper or paper-based media; and any type of mediaor device suitable for storing instructions and/or information. Variousembodiments include a computer program product that can be transmittedin whole or in parts and over one or more public and/or private networkswherein the transmission includes instructions which can be used by oneor more processors to perform any of the features presented herein. Invarious embodiments, the transmission may include a plurality ofseparate transmissions.

Stored one or more of the computer readable medium (media), the presentdisclosure includes software for controlling both the hardware ofgeneral purpose/specialized computer(s) and/or processor(s), and forenabling the computer(s) and/or processor(s) to interact with a humanuser or other mechanism utilizing the results of the present invention.Such software may include, but is not limited to, device drivers,operating systems, execution environments/containers, user interfacesand applications.

The foregoing description of the preferred embodiments of the presentinvention has been provided for purposes of illustration anddescription. It is not intended to be exhaustive or to limit theinvention to the precise forms disclosed. Many modifications andvariations can be apparent to the practitioner skilled in the art.Embodiments were chosen and described in order to best explain theprinciples of the invention and its practical application, therebyenabling others skilled in the relevant art to understand the invention.It is intended that the scope of the invention be defined by thefollowing claims and their equivalents.

1. A telecommunications system, comprising: an application interface toreceive at least one invocation to a legacy short message peer-to-peerprotocol from a legacy application; a gatekeeper to control accessthrough the telecommunications system by applying at least one policy tothe invocation; wherein the at least one policy indicates whether thelegacy application is permitted to use a resource of thetelecommunications system; and a resource interface connecting thegatekeeper with at least one resource element implementing the legacyshort message peer-to-peer protocol to receive the at least oneinvocation to a legacy short message peer-to-peer protocol when thegatekeeper permits the legacy application to use a resource of thetelecommunications system.
 2. The telecommunications system of claim 1,wherein an application interface to receive at least one invocation to alegacy short message peer-to-peer protocol from a legacy applicationincludes: an application interface to receive at least one invocation toa legacy Short Message Peer-to-Peer Protocol (SMPP) from a legacyapplication.
 3. The telecommunications system of claim 1, wherein agatekeeper to control access through the telecommunications system byapplying at least one policy to the invocation; wherein the at least onepolicy indicates whether the legacy application is permitted to use aresource of the telecommunications system includes: a policy engine atthe gatekeeper to control access through the telecommunications systemby applying at least one policy in accordance with a service levelagreement (SLA) to the invocation.
 4. The telecommunications system ofclaim 1, wherein a resource interface connecting the gatekeeper with atleast one resource element implementing the legacy short messagepeer-to-peer protocol to receive the at least one invocation to a legacyshort message peer-to-peer protocol when the gatekeeper permits thelegacy application to use a resource of the telecommunications systemincludes: a resource interface plug-in connecting the gatekeeper with atleast one resource element implementing the legacy Short MessagePeer-to-Peer Protocol (SMPP).
 5. The telecommunications system of claim1, further comprising: a Message Center coupled with the resourceinterface to provide a data communications interface for transfer ofshort message data.
 6. The telecommunications system of claim 5, whereinthe Message Center coupled with the resource interface to provide a datacommunications interface for transfer of short message data includes atleast one of a Short Message Service Center (SMSC), a Global System forMobile communications (GSM) Unstructured Services Data (USSD) Server anda Short Messaging Service (SMS) application system.
 7. Thetelecommunications system of claim 6, wherein the SMS application systemincludes at least one of a Wireless Application Protocol (WAP) ProxyServer, an email gateway, and a messaging gateway.
 8. A method forcontrolling access to a legacy short message peer-to-peer protocol basedupon a policy in a telecommunications environment, the methodcomprising: receiving, by an application interface, at least oneinvocation to a legacy short message peer-to-peer protocol from a legacyapplication; controlling access through the telecommunications system byapplying at least one policy to the invocation at a gatekeeper; whereinthe at least one policy indicates whether the legacy application ispermitted to use a resource of the telecommunications system; andproviding to a resource interface connecting the gatekeeper with atleast one resource element implementing the legacy short messagepeer-to-peer protocol, the at least one invocation to a legacy shortmessage peer-to-peer protocol when the gatekeeper permits the legacyapplication to use a resource of the telecommunications system.
 9. Themethod of claim 8, wherein receiving, by an application interface, atleast one invocation to a legacy short message peer-to-peer protocolfrom a legacy application includes: receiving at least one invocation toa legacy Short Message Peer-to-Peer Protocol (SMPP) from a legacyapplication.
 10. The method of claim 8, wherein controlling accessthrough the telecommunications system by applying at least one policy tothe invocation at a gatekeeper; wherein the at least one policyindicates whether the legacy application is permitted to use a resourceof the telecommunications system includes: controlling access throughthe telecommunications system using a policy engine at the gatekeeper toapply at least one policy in accordance with a service level agreement(SLA) to the invocation.
 11. The method of claim 8, wherein providing toa resource interface connecting the gatekeeper with at least oneresource element implementing the legacy short message peer-to-peerprotocol, the at least one invocation to a legacy short messagepeer-to-peer protocol when the gatekeeper permits the legacy applicationto use a resource of the telecommunications system includes: providingto a resource interface plug-in connecting the gatekeeper with at leastone resource element implementing the legacy Short Message Peer-to-PeerProtocol (SMPP), the at least one invocation to a legacy short messagepeer-to-peer protocol when the gatekeeper permits the legacy applicationto use a resource of the telecommunications system.
 12. The method ofclaim 8, further comprising: providing a data communications interfacefor transfer of short message data via a Message Center coupled with theresource interface.
 13. The method of claim 12, wherein providing a datacommunications interface for transfer of short message data via aMessage Center coupled with the resource interface includes: providing adata communications interface for transfer of short message data via atleast one of a Short Message Service Center (SMSC), a Global System forMobile communications (GSM) Unstructured Services Data (USSD) Server anda Short Messaging Service (SMS) application system.
 14. The method ofclaim 13, wherein providing a data communications interface for transferof short message data via the SMS application system includes: providinga data communications interface for transfer of short message data viaat least one of a Wireless Application Protocol (WAP) Proxy Server, anemail gateway, and a messaging gateway.
 15. An apparatus for controllingaccess to legacy short message peer-to-peer protocol in atelecommunications system, the apparatus comprising: a processor; andone or more stored sequences of instructions which, when executed by theprocessor, cause the processor to carry out the steps of: receiving, byan application interface, at least one invocation to a legacy shortmessage peer-to-peer protocol from a legacy application; controllingaccess through the telecommunications system by applying at least onepolicy to the invocation at a gatekeeper; wherein the at least onepolicy indicates whether the legacy application is permitted to use aresource of the telecommunications system; and providing to a resourceinterface connecting the gatekeeper with at least one resource elementimplementing the legacy short message peer-to-peer protocol, the atleast one invocation to a legacy short message peer-to-peer protocolwhen the gatekeeper permits the legacy application to use a resource ofthe telecommunications system.